-
Notifications
You must be signed in to change notification settings - Fork 185
Expose Plot.channel and Plot.transform #411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
0153e5d
to
38c2452
Compare
Rewritten; this time I've left out the renaming of maybeLazyChannel into column, and basic into transform, since it only creates merge conflicts. But when (if) we merge, it would be good to rename these functions internally. |
Looks like the documentation needs updating here, since Plot.transform now takes (options, transform) rather than (...transforms)? |
Also, do we want to expose maybeLazyChannel here, or lazyChannel? My inclination is that I’d prefer Plot.column to be an alias for the latter, so that a setter function is always returned (even if there is no source input). |
38c2452
to
8dab9dc
Compare
rebased with fixes to the documentation and adoption of lazyChannel instead of maybeLazyChannel. |
helpers to create custom transforms (#170)
An example uses Plot.transform to create a uniform sample transform (diamond-carat-sampling)
An example of Plot.column is available at https://observablehq.com/@fil/plot-splom